Topic 4: Project Integration Management

Project Integration Management (PIM) is the knowledge area that involves managing the project as a whole — keeping the "big picture" in view while coordinating all other project management knowledge areas throughout the project's life cycle.

It is considered the key to overall project success because:

• The project manager must ensure all elements of the project are properly coordinated — scope, time, cost, quality, risk, etc.
• Many new project managers focus on too many details and lose sight of the big picture; PIM prevents this.
• All seven integration processes span the entire project life cycle from initiation to closure.

The seven processes of Project Integration Management are:

• 1. Develop Project Charter — Formally authorizes the project and documents the project's objectives and stakeholder agreement.
• 2. Develop Preliminary Project Scope Statement — Captures high-level scope requirements to give direction early in the project.
• 3. Develop Project Management Plan — Coordinates all planning documents into one consistent, coherent plan.
• 4. Direct & Manage Project Execution — Carries out the project management plan by performing all planned activities.
• 5. Monitor & Control Project Work — Tracks, reviews, and oversees project progress against performance objectives.
• 6. Perform Integrated Change Control — Coordinates changes affecting deliverables and organizational process assets.
• 7. Close the Project — Finalizes all activities and formally closes the project or phase.

Strategic planning involves determining long-term objectives, predicting future trends, and projecting the need for new products and services. It provides the foundation for selecting which IT projects to pursue.

Analysis tools used:

• SWOT Analysis — evaluates Strengths, Weaknesses, Opportunities, and Threats of the organization.
• Porter's Five Forces Analysis — examines competitive forces: bargaining power of suppliers/customers, threat of new entrants/substitutes, and rivalry among competitors.

Four stages of the IT Planning Process (pyramid model):

• IT Strategy Planning — Ties IT strategy to the mission and vision; identifies key business areas.
• Business Area Analysis — Documents key business processes that could benefit from IT.
• Project Planning — Defines potential projects, scope, benefits, and constraints.
• Resource Allocation — Selects IT projects and assigns resources.

1. Net Present Value (NPV) Analysis

NPV calculates the expected net monetary gain or loss from a project by discounting all expected future cash inflows and outflows to the present point in time. It accounts for the time value of money.

2. Return on Investment (ROI)

ROI measures the efficiency of an investment as a percentage.

3. Payback Analysis

The payback period is how long it takes for cumulative net benefits to equal cumulative costs (i.e., when the cumulative benefits − costs = 0). Most organizations prefer a short payback period for IT projects.

• IRR (Internal Rate of Return) is the discount rate at which NPV = 0; it indicates efficiency/yield of the investment.
• If IRR > minimum acceptable rate of return → investment is acceptable.

A Project Charter is a document that formally recognizes the existence of a project and provides direction on the project's objectives and management. It authorizes the project manager to use organizational resources.

Key contents of a Project Charter include:

• Project title and date of authorization
• Brief description of project objectives and business justification
• Summary schedule with planned start and finish dates
• Summary budget or reference to budgetary documents
• Project success criteria and approval requirements
• Stakeholder needs, important assumptions, and constraints
• Roles and responsibilities matrix
• Signatures of key project stakeholders

A Scope Statement is a document used to develop and confirm a common understanding of the project scope. The preliminary version is created early during project initiation; a more detailed version is developed as the project progresses.

Key contents of a Preliminary Scope Statement:

• Project objectives
• Product or service requirements and characteristics
• Project boundaries and deliverables
• Product acceptance criteria
• Project assumptions and constraints
• Organizational structure for the project
• Initial list of defined risks
• Summary of schedule milestones
• Rough order of magnitude cost estimate
• Configuration management requirements
• Description of approval requirements

A Project Management Plan is a document used to coordinate all project planning documents and help guide a project's execution and control. Plans from all other knowledge areas (scope, time, cost, risk, etc.) become subsidiary parts of this overall plan.

Key Attributes of a Good Project Plan:

• Dynamic — evolves as the project changes
• Flexible — adapts to new information
• Updated as changes occur
• Primarily guides project execution, helping the PM lead the team and assess status

Major Content Sections (per IEEE Standard 1058-1998 / SPMP):

• Overview — Purpose, scope, objectives, assumptions, schedule & budget summary
• Project Organization — External/internal structure, roles & responsibilities
• Managerial Process Plans — Start-up, staffing, resource acquisition, work plan, risk management, closeout
• Technical Process Plans — Process model, methods, tools, infrastructure, product acceptance
• Supporting Process Plans — Configuration management, verification, documentation, quality assurance

Project Execution involves managing and performing the work described in the project management plan. The majority of time and money is spent during this phase.

Key Tools and Techniques:

• Project Management Methodology — A formal approach describing not just what to do but how to do it. Most effective way to improve project management.
• Expert Judgements — Consulting specialists on methodology, programming language choice, training approach, etc.
• Meetings — Face-to-face, phone, and virtual meetings that build relationships and resolve problems through dialogue.
• Project Management Artifacts — Tabular/graphical tools like project estimates, PERT charts, Gantt charts, budget sheets, and risks/issues lists.
• Project Management Information Systems (PMIS) — Enterprise PM software accessible via the Internet that integrates all project data.

Essential Skills for Project Execution:

• General management skills: leadership, communication, and political skills
• Product, business, and application area knowledge
• Use of specialized tools and techniques

Former (Old) View:

• The project team should execute exactly what was planned, on time and within budget.
• Problem: Stakeholders rarely agreed on scope beforehand, and estimates were often inaccurate, making this view impractical.

Modern (New) View:

• Project management is a process of constant communication and negotiation.
• Solution: Changes are often beneficial — the project team should plan for them proactively.

Change Control System: A formal, documented process describing when and how official project documents may be changed, and who is authorized to make them.

Change Control Board (CCB):

• A formal group of people responsible for approving or rejecting changes on a project.
• Provides guidelines for preparing change requests, evaluates them, and manages implementation of approved changes.
• Includes stakeholders from the entire organization.
• In agile environments, a "48-hour policy" can allow timely decisions without waiting for the next CCB meeting.

Three objectives of Integrated Change Control: (1) Influence change factors to ensure changes are beneficial, (2) Determine that a change has occurred, (3) Manage actual changes as they occur.

Weighted Scoring Model:

A tool that provides a systematic process for selecting projects based on multiple criteria. Each criterion is assigned a weight (importance), and each project is scored against each criterion.

Example criteria for IT projects:

• Supports key business objectives (25%)
• Has strong internal sponsor (15%)
• Has strong customer support (15%)
• Provides positive NPV (20%)
• Has low risk in meeting scope, time, cost (10%)

Balanced Scorecard:

A methodology that converts an organization's value drivers — such as customer service, innovation, operational efficiency, and financial performance — into a series of defined metrics. Organizations analyze these metrics to determine how well projects help achieve strategic goals. It takes a broader, more strategic view across four perspectives:

• Customer Perspective — e.g., improve client satisfaction
• Financial Perspective — e.g., reduce cost, expand competitive sourcing
• Internal Perspective — e.g., improve quality, encourage innovation
• Growth & Learning Perspective — e.g., enhance employee competence